components/workspace/intent-bar.tsx (1)

145-147: Constrain reader-text panel height to avoid layout push on long responses.

Long readerText payloads can dominate vertical space and bury the input. Consider adding a max height with internal scroll.

🧩 Suggested tweak

-<pre className="mt-2 whitespace-pre-wrap text-xs text-muted-foreground">
+<pre className="mt-2 max-h-56 overflow-auto whitespace-pre-wrap text-xs text-muted-foreground">
   {infoResponse.readerText}
 </pre>

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@components/workspace/intent-bar.tsx` around lines 145 - 147, The readerText
<pre> in intent-bar.tsx can grow arbitrarily and push the layout; constrain its
height and enable internal scrolling by giving the <pre> rendering
infoResponse.readerText a max-height (e.g., via a class or inline style) and
overflow-y: auto so long responses scroll instead of expanding; update the
element that renders infoResponse.readerText (the <pre> with className "mt-2
whitespace-pre-wrap text-xs text-muted-foreground") to include the
maxHeight/overflow styling so the input area is not pushed offscreen.

components/workspace/workspace-provider.tsx (1)

689-701: Extract duplicated informational-response parsing into a shared helper.

The two submit paths now duplicate the same parse/branch/cast flow. Consolidating this will reduce drift risk and make future schema changes safer.

♻️ Suggested direction

+function normalizeOrchestratorResponse(
+  data: z.infer<typeof OrchestratorResponseSchema>,
+): { kind: "info"; info: { reasoning: string; readerText?: string; suggestions?: string[] } }
+ | { kind: "changeset"; changeset: ChangeSet } {
+  const { changeSet: rawCs, reasoning, readerText, suggestions } = data;
+  if (!rawCs || !Array.isArray(rawCs.operations) || rawCs.operations.length === 0) {
+    return { kind: "info", info: { reasoning, readerText, suggestions } };
+  }
+  return { kind: "changeset", changeset: rawCs as unknown as ChangeSet };
+}

Then both submitIntent and submitIntentForProduct can call the same helper.

Also applies to: 750-760

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@components/workspace/workspace-provider.tsx` around lines 689 - 701, The
parsing and informational-response branch (reading validated.data -> {
changeSet: rawCs, reasoning, readerText, suggestions } then checking
rawCs/operations, calling setDraftChangeset/setInfoResponse/setPhase and casting
rawCs to ChangeSet as cs) is duplicated between submitIntent and
submitIntentForProduct; extract this logic into a single helper (e.g.,
parseOrHandleInfoResponse or processValidatedChangeSet) that accepts
validated.data and the setters (setDraftChangeset, setInfoResponse, setPhase)
and returns either a typed ChangeSet or null, preserve the existing runtime
checks (Array.isArray(rawCs.operations) && length > 0) and the unsafe cast
through unknown to ChangeSet, and replace the duplicated blocks in submitIntent
and submitIntentForProduct with calls to that helper.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes